-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pivot phase to clusterctl and unify pivoting approach #731
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
first pass review
return nil, err | ||
} | ||
|
||
if out.TypeMeta.Kind == "StatefulSet" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we log a warning if this case is not matched saying we're ignoring something?
b1fede7
to
049b558
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of great work in this PR. Left some comments.
One clarification: the PR adds a new way to pivot resources, but doesn't change the current way when not using phases, is that correct? |
No, this both adds the phase and updates the pivot logic for both the |
Got it, we should update title and description then. |
611552e
to
a50ae6d
Compare
1ec078c
to
c5fcf48
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments, otherwise LGTM! 🎉
- Add `clusterctl alpha phases pivot` subcommand - Pivot ClusterAPI objects for all namespaces - Adds MachineClass support to pivoting - Unify pivoting approach - Scale down StatefulSets on pivot to avoid dueling controllers - Remove ownerRefs prior to pivoting objects - Change order of pivoting of Machine* objects to avoid race conditions - Recursively copy objects based on ownerRefs - `clusterctl delete cluster` now pivots and deletes Cluster API resources from all namespaces. Co-authored-by: Chuck Ha <[email protected]> Signed-off-by: Jason DeTiberus <[email protected]>
/test pull-cluster-api-test |
arrgh, |
/test pull-cluster-api-test |
46b405e
to
71d559a
Compare
/test pull-cluster-api-test |
I think this might need a rebase now that fetch-tools has been removed in the other PR. |
@vincepri that was only for cluster-api-provider-aws, it proved to still be in use for this repo |
Argh, I see. Hopefully it'll be fixes soon by kubebuilder folks. |
@vincepri I triggered the last test to verify that it was working after hearing back from the kubebuilder team :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
We should wait to merge it until early next week in case other folks have any more comments, wdyt?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: detiber, vincepri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
What this PR does / why we need it:
clusterctl delete cluster
now pivots and deletes Cluster APIresources from all namespaces.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Related to #554
Fixes: #448
Release note: